Digital Processing System for Event and/or Time Based Triggering Management, and Control of Tasks

ABSTRACT

A method, apparatus, computer-readable medium, and/or system may comprise a user device configured to receive, from a user, a selection of a plurality of dependent computing tasks for a first computing task. The user device may transmit, to a computing device, the selection of the plurality of dependent computing tasks for the first computing task. The system may comprise a computing device comprising a processor and memory storing computer-executable instructions that, when executed by the processor, cause the computing device to receive, from the user device, the selection of the plurality of dependent computing tasks for the first computing task. The computing device may store, at a task registry and in association with the first computing task, an indication of the plurality of dependent computing tasks. The computing device may cause transmission of the first computing task from the task registry to a task queue. In some aspects, a dependent task queue may comprise the plurality of dependent computing tasks. The computing device may determine whether the plurality of dependent computing tasks has been executed. If the plurality of dependent computing tasks has been executed, the computing device may determine one or more nodes for executing the first computing task and cause transmission of the first computing task from the task queue to the one or more nodes for executing the first computing task. The one or more nodes may be configured to execute the first computing task in response to receiving the first computing task from the task queue.

CROSS-REFERENCE TO RELATED APPLICATION

This application is a continuation of U.S. patent application Ser. No.15/483,212 entitled “Digital Processing System for Event and/or TimeBased Triggering, Management, and Control of Tasks” filed on Apr. 10,2017. This application claims priority to and the benefit of theabove-identified application which is fully incorporated by referenceherein in its entirety.

TECHNICAL FIELD

One or more aspects of the disclosure generally relate to computingdevices, computing systems, and computer software. In particular, one ormore aspects of the disclosure generally relate to computing devices,computing systems, and computer software that may be used to trigger,manage, and/or control computing tasks based on events and/or timefactors

BACKGROUND

Computing systems may need to perform numerous computing tasks. However,performance of these tasks by existing systems may be time consuming, orexisting sequential execution of tasks may result in one or more tasksnot being performed. What is needed is a more efficient and accurate wayof executing computing tasks, such as sequential execution of tasks.

SUMMARY

The following presents a simplified summary in order to provide a basicunderstanding of some aspects of the disclosure. The summary is not anextensive overview of the disclosure. It is neither intended to identifykey or critical elements of the disclosure nor to delineate the scope ofthe disclosure. The following summary merely presents some concepts ofthe disclosure in a simplified form as a prelude to the descriptionbelow.

A method, apparatus, computer-readable medium, and/or system maycomprise a user device configured to receive, from a user, a selectionof a plurality of dependent computing tasks for a first computing task.The user device may transmit, to a computing device, the selection ofthe plurality of dependent computing tasks for the first computing task.The system may comprise a computing device comprising a processor andmemory storing computer-executable instructions that, when executed bythe processor, cause the computing device to receive, from the userdevice, the selection of the plurality of dependent computing tasks forthe first computing task. The computing device may store, at a taskregistry and in association with the first computing task, an indicationof the plurality of dependent computing tasks. The computing device maycause transmission of the first computing task from the task registry toa task queue. In some aspects, a dependent task queue may comprise theplurality of dependent computing tasks. The computing device maydetermine whether the plurality of dependent computing tasks has beenexecuted. If the plurality of dependent computing tasks has beenexecuted, the computing device may determine one or more nodes forexecuting the first computing task and cause transmission of the firstcomputing task from the task queue to the one or more nodes forexecuting the first computing task. The one or more nodes may beconfigured to execute the first computing task in response to receivingthe first computing task from the task queue.

In some aspects, determining whether the plurality of dependentcomputing tasks has been executed may comprise determining whetherexecution of the plurality of dependent computing tasks has beencompleted by one or more nodes. Determining whether the plurality ofdependent computing tasks has been executed may additionally oralternatively comprise determining whether execution of the plurality ofdependent computing tasks has been initiated by one or more nodes.

In some aspects, the memory of the computing device may storecomputer-executable instructions that, when executed by the processor,cause the computing device to cause transmission of the plurality ofdependent computing tasks from the task registry to the dependent taskqueue. Causing the transmission of the first computing task from thetask registry to the task queue may be performed before causing thetransmission of the plurality of dependent computing tasks from the taskregistry to the dependent task queue.

In some aspects, the memory of the computing device may storecomputer-executable instructions that, when executed by the processor,cause the computing device to determine whether the computing device hasreceived a manual override from the user device. If the computing devicehas received the manual override from the user device, the computingdevice may determine one or more nodes for executing the first computingtask and may cause transmission of the first computing task from thetask queue to the one or more nodes for executing the first computingtask.

In some aspects, the memory of the computing device may storecomputer-executable instructions that, when executed by the processor,cause the computing device to determine whether a current time exceeds ascheduled time to execute the first computing task. If the current timeexceeds the scheduled time to execute the first computing task, thecomputing device may determine one or more nodes for executing the firstcomputing task and may cause transmission of the first computing taskfrom the task queue to the one or more nodes for executing the firstcomputing task.

In some aspects, the memory of the computing device may storecomputer-executable instructions that, when executed by the processor,cause the computing device to determine one or more nodes for executingthe first computing task. The computing device may determine, based onthe one or more nodes for executing the first computing task, an amountof time to complete execution of the first computing task. The computingdevice may determine, based on the amount of time to complete executionof the first computing task, a latest time to execute the firstcomputing task.

BRIEF DESCRIPTION OF THE DRAWINGS

The present disclosure is illustrated by way of example and not limitedin the accompanying figures in which like reference numerals indicatesimilar elements and in which:

FIG. 1 illustrates an example operating environment in which variousaspects of the disclosure may be implemented.

FIG. 2 illustrates another example operating environment in whichvarious aspects of the disclosure may be implemented.

FIG. 3 illustrates an example of at least a portion of a flow diagramfor triggering, managing, and/or controlling computing tasks based onevents and/or time factors in which various aspects of the disclosuremay be implemented.

FIG. 4 illustrates another example of at least a portion of a flowdiagram for triggering, managing, and/or controlling computing tasksbased on events and/or time factors in which various aspects of thedisclosure may be implemented.

FIG. 5 illustrates an example user interface for triggering, managing,and/or controlling computing tasks based on events and/or time factorsin which various aspects of the disclosure may be implemented.

DETAILED DESCRIPTION

In the following description of various illustrative embodiments,reference is made to the accompanying drawings, which form a parthereof, and in which is shown, by way of illustration, variousembodiments in which the claimed subject matter may be practiced. It isto be understood that other embodiments may be utilized, and thatstructural and functional modifications may be made, without departingfrom the scope of the present claimed subject matter.

FIG. 1 illustrates an example operating environment in which variousaspects of the disclosure may be implemented. An illustrative system 100for implementing methods according to the present disclosure is shown.System 100 may include a task management computing device 101. As willbe described in further detail below, the computing device 101 mayfacilitate triggering, managing, and/or controlling computing tasksbased on events and/or time factors. In some aspects, the system 100 mayfacilitate triggering, managing, and/or controlling tasks in a midrangeserver environment, which may result in more efficient and fasterinterfacing and communication of task data with one or more servers 121or 131. Moreover, and as will be described in further detail below, useof one or more server nodes and/or server node clusters in a network151, such as with load balancing and load management services, mayresult in faster execution of tasks. Exemplary tasks may include end ofday processes, end of day data (e.g., financial) totals, database purge,or other computing tasks.

The computing device 101 may have a processor 103 for controllingoverall operation of the computing device and its associated components,including for example random access memory (RAM) 105, read-only memory(ROM) 107, input/output (I/O) module 109, and memory 111. I/O module 109may include, e.g., a microphone, mouse, keypad, touch screen, scanner,optical reader, and/or stylus (or other input device(s)) through which auser of computing device 101 may provide input, and may also include oneor more of a speaker for providing audio output and a video displaydevice for providing textual, audiovisual, and/or graphical output.Software may be stored within memory 111 and/or other storage to provideinstructions to processor 103 for enabling computing device 101 toperform various functions. For example, memory 111 may store softwareused by the computing device 101, such as an operating system 113,application programs 115, and an associated database 117. Additionallyor alternatively, some or all of the computer executable instructionsfor computing device 101 may be embodied in hardware or firmware (notshown).

The computing device 101 may operate in a networked environmentsupporting connections to one or more other computers, such as server121 and server 131 (or other devices). The servers 121 and 131 maycomprise servers that include any or all of the elements described abovewith respect to the computing device 101. The network connectionsdepicted in FIG. 1 include a local area network (LAN), and a wide areanetwork (WAN), but may also include other networks. The computing device101 may communicate with other computing devices using a communicationinterface 119 or other network interface for establishing communicationsover a LAN and/or a WAN, such as the Internet. It will be appreciatedthat the network connections shown are illustrative and other means ofestablishing a communications link between the computers may be used.The existence of any of various well-known protocols such as TCP/IP,Ethernet, FTP, HTTP, HTTPS, and the like is presumed.

System 100 may also include one or more servers 121 and 131 (and otherservers, which are not illustrated), which may be any suitable server,processor, computer, or data processing device, or combination of thesame. Servers 121 and/or 131 may each be owned, managed, and/or operatedby a particular team and/or business unit. Servers 121 and/or 131 may beconnected by one or more communications links 181 and 183 to network151. As will be described in further detail in the examples below,servers 121 and 131 may communicate, via a communication session, data(e.g., computing tasks or data relating to computing tasks) to otherdevices, such as the task management computing device 101, user devices151 (e.g., laptop, workstation, mobile device, and the like), and/or orother devices. Any of the elements in FIG. 1 may be implemented as oneor more computing device, such as the example computing device 201described in connection with FIG. 2 below.

Network 151 may be any suitable network including a cloud network, theInternet, an intranet, a wide-area network (WAN), a local-area network(LAN), a wireless network, a digital subscriber line (DSL) network, aframe relay network, an asynchronous transfer mode (ATM) network, avirtual private network (VPN), a cellular network, or any combination ofany of the same. The network 151 may comprise one or more nodes (e.g.,server nodes) and/or node clusters for executing one or more tasks.Communications links 181, 183, 185, 187, or other communication linksmay be any communications links suitable for communicating among thetask management computing device 101, servers 121 and 131, user devices151, and/or other devices, such as network links, dial-up links,wireless links, hard-wired links, or other communications links.

The user device 151 may be used, such as by a user associated with theserver 121 and/or server 131, to receive task and/or task-relatedinformation. The user device 151 may include input devices for receivinguser input, such as a touchscreen display, a physical keyboard, amicrophone, a mouse, and the like. For example, the user interface 500illustrated in FIG. 5, which will be described in further detail below,may be used to receive the task and/or task-related information from auser. The user device 151 may transmit the task and/or task-relatedinformation to the task management computing device 101.

The system 100 may also comprise a task registry 161. The task registry161 may be used to receive and/or store task information, which may beexecuted in the future. In some aspects, the task registry 161 may bepart of the task management computing device 101 and/or may be part of adifferent computing device located at a different location from the taskmanagement computing device 101. The task registry 161 may comprise, forexample, a registry table used to identify and/or define tasks and tostore parameters for tasks.

The system 100 may also comprise a dependent task registry 163. Thedependent task registry 163 may be used to receive and/or storedependent task information, which may be executed in the future (or mayhave been executed in the past). In some aspects, the dependent taskregistry 163 may be part of the task management computing device 101and/or may be part of a different computing device located at adifferent location from the task management computing device 101. Thedependent task registry 163 may comprise, for example, a dependentregistry table used to identify and/or define dependent tasks and tostore parameters for dependent tasks.

The system 100 may also comprise a task queue 171. The task queue 171may be used to receive, such as from the task registry 161, tasks to beexecuted. The task queue 171 may be part of the task managementcomputing device 101 and/or may be part of a different computing devicelocated at a different location from the task management computingdevice 101. When a task is ready to be executed, the task queue 171 maysend the task to one or more node or node cluster 141 of the network 151for execution. The task queue 171 may be used to manage active tasks(e.g., tasks currently being executed) and/or tasks waiting to beexecuted. Load balancing may be used to select the node 141 or nodecluster(s) to execute a task.

The system 100 may also comprise a dependent task queue 173. Thedependent task queue 173 may be used to receive, such as from thedependent task registry 163, dependent tasks to be executed (or anindication of dependent tasks already executed). The dependent taskqueue 173 may be part of the task management computing device 101 and/ormay be part of a different computing device located at a differentlocation from the task management computing device 101. When a dependenttask is ready to be executed, the dependent task queue 173 may send thedependent task to one or more node or node cluster 141 of the network151 for execution. The dependent task queue 173 may be used to manageactive dependent tasks (e.g., dependent tasks currently being executed)and/or tasks waiting to be executed. Load balancing may be used toselect the node 141 or node cluster(s) to execute a dependent task.

FIG. 2 illustrates an example block diagram of a computing device 201(e.g., a computer server, desktop computer, laptop computer, tabletcomputer, other computing devices) in an example computing environment200 that may be used according to one or more illustrative embodimentsof the disclosure. The computing device 201 may have a processor 203 forcontrolling overall operation of the server and its associatedcomponents, including for example random access memory (RAM) 205,read-only memory (ROM) 207, input/output (I/O) module 209, and memory215.

I/O module 209 may include, e.g., a microphone, mouse, keypad, touchscreen, scanner, optical reader, and/or stylus (or other inputdevice(s)) through which a user of computing device 201 may provideinput, and may also include one or more of a speaker for providing audiooutput and a video display device for providing textual, audiovisual,and/or graphical output. Software may be stored within memory 215 and/orother storage to provide instructions to processor 203 for enablingcomputing device 201 to perform various functions. For example, memory215 may store software used by the computing device 201, such as anoperating system 217, application programs 219, and an associateddatabase 221. Additionally or alternatively, some or all of the computerexecutable instructions for computing device 201 may be embodied inhardware or firmware (not shown).

The computing device 201 may operate in a networked environmentsupporting connections to one or more remote computers, such asterminals 241 and 251. The terminals 241 and 251 may be personalcomputers or servers that include any or all of the elements describedabove with respect to the computing device 201. The network connectionsdepicted in FIG. 2 include a local area network (LAN) 225 and a widearea network (WAN) 229, but may also include other networks. When usedin a LAN networking environment, the computing device 201 may beconnected to the LAN 225 through a network interface or adapter 223.When used in a WAN networking environment, the computing device 201 mayinclude a modem 227 or other network interface for establishingcommunications over the WAN 229, such as the Internet 231. It will beappreciated that the network connections shown are illustrative andother means of establishing a communications link between the computersmay be used. The existence of any of various well-known protocols suchas TCP/IP, Ethernet, FTP, HTTP, HTTPS, and the like is presumed.Computing device 201 and/or terminals 241 or 251 may also be mobiledevices (e.g., mobile phones, smartphones, PDAs, notebooks, tablets,other mobile devices) including various other components, such as abattery, speaker, and antennas.

FIG. 3 illustrates an example of at least a portion of a flow diagramfor triggering, managing, and/or controlling computing tasks based onevents and/or time factors in which various aspects of the disclosuremay be implemented.

In step 302, the task management computing device 101 may determinewhether it received task information. For example, the computing device101 may receive task information from a server 121 or server 131 (e.g.,in an automated process) or may receive task information from a userdevice 151, which may be inputted by a user of the user device 151. Ifthe computing device 101 has not received task information (step 302:N), the computing device 151 may wait to receive task information. Ifthe computing device 101 determines it has received task information(step 302: Y), the computing device 101 may proceed to step 304. Taskinformation may comprise, for example, a unique identifier for a task, adescription for the task, an indication of whether the task istime-based (e.g., triggered by time) or event-based (e.g., triggered byother the execution of other task(s)), a scheduled time for executingthe task, a due out time for the task, event trigger dependencies forthe task (e.g., which tasks are to be executed, whether initiated orcompleted, prior to execution of the current task), and/or otherinformation relating to a task. As will be described in further detailbelow, after task information is updated or generated, the taskmanagement computing device 101 may store, such as in the task registry161 and/or the dependent task registry 163, the task information inassociation with the task (e.g., via the unique identifier for thetask). In some aspects, entries in a task registry 161 table ordependent task registry 163 table may be used to store values for eachpiece of task information. For example, a column with associated entriesmay be used to indicate one or more trigger dependencies, another columnmay be used to indicate the due out time for the task, and anothercolumn may be used to indicate the scheduled time of execution for thetask.

In step 304, the task management computing device 101 may determinewhether the received task information relates to an update to anexisting task. If the received information relates to an update to anexisting task (step 304: Y), the computing device 101 may proceed tostep 308. If the received task information does not relate to an updateto an existing task (step 304: N), the computing device may determinethat the information relates to a new task and proceed to step 306.

In step 306, the task management computing device 101 may generate aunique identifier for the new task. The unique identifier may be anyalphanumeric combination of characters used to distinguish a task fromother tasks in the system 100 or managed by the computing device 101.The unique task identifier may be used to, for example, prevent thecreation of duplicate tasks.

In step 308, the task management computing device 101 may determinewhether to update (e.g., for an existing task) or generate (e.g., for anew task or an existing task without an indication of whether the taskis time or event-based) an indication of whether the task is triggeredby a time or an event (e.g., initiation or completion of another task).If the computing device 101 determines to update or generate theindication of whether the task is time or event-based (step 308: Y), thecomputing device 101 may update or generate the indication of whetherthe task is time or event-based in step 310. If the computing device 101determines that the received task information does not indicate whetherthe task is time or event-based (step 308: N), the computing device 101may proceed to step 312.

In step 312, the task management computing device 101 may determinewhether to update (e.g., for an existing task) or generate (e.g., for anew task or an existing task without a time of execution) a scheduledtime of execution. In some aspects, tasks may be triggered by apredefined time schedule, and the time of execution may indicate a timeto execute a particular task, such as if the task is triggered by thecurrent time exceeding the time of execution. If the computing device101 determines to update or generate the time of execution (step 312:Y), the computing device 101 may update or generate the time ofexecution for the task in step 314. If the computing device 101determines that the received task information does not indicate a timeof execution for the task (step 312: N), the computing device 101 mayproceed to step 316.

In step 316, the task management computing device 101 may determinewhether to update (e.g., for an existing task) or generate (e.g., for anew task or an existing task without a time of completion) a due outtime for the task. For example, the system 100 may execute a task (ormark the task as complete) so that it is completed before a particulartime (e.g., 4 PM) or spends a particular amount of time in the taskqueue (e.g., 10 minutes), even if the time-based or event-based triggersfor the task have not yet occurred. Accordingly, the due out time mayact as an override for the time-based or event-based triggers in someaspects. For example, a task may become stale if it remains in the taskqueue 171 without being executed for more than a threshold amount oftime (e.g., 3 days). The due out time parameter may be used to preventstale tasks from using bandwidth and/or processing resources in the taskqueue 171. If the computing device 101 determines to update or generatethe due out time (step 316: Y), the computing device 101 may update orgenerate the due out time for the task in step 318. If the computingdevice 101 determines that the received task information does notindicate a due out time for the task (step 316: N), the computing device101 may proceed to step 320.

In step 320, the task management computing device 101 may determinewhether to update (e.g., for an existing task) or generate (e.g., for anew task or an existing task without trigger dependencies) triggerdependencies for the task, such as other tasks to be completed,executed, and/or initiated before executing the task. In an exemplarymany-to-one task dependency scenario, 3 tasks (e.g., dependent tasks)may have to be executed (e.g., initiated and/or completed) beforeanother task is to be executed. In an exemplary many-to-many taskdependency scenario, 3 tasks (e.g., dependent tasks) may have to beexecuted before another 5 tasks are to be executed. In an exemplaryone-to-many task dependency, 1 task may have to be executed beforeanother 4 tasks are to be executed. For example, the task may triggerthe execution of 4 other tasks. If the computing device 101 determinesto update or generate the trigger dependencies (step 320: Y), thecomputing device 101 may update or generate the trigger dependencies instep 322. If the computing device 101 determines that the received taskinformation does not indicate an update to trigger dependencies (step320: N), the computing device 101 may return to step 302 to determinewhether the computing device 101 has received task information foranother task. In some aspects, the computing device 101 may validate anyof the task information previously described prior to storing the taskinformation in, for example, the task registry 161 and/or the dependenttask registry 163.

FIG. 5 illustrates an example user interface 500 for triggering,managing, and/or controlling computing tasks based on events and/or timefactors in which various aspects of the disclosure may be implemented.In some aspects, a user, via a user device 151, may update or provideone or more parameters (e.g., task information previously described) fortasks via the user interface 500. For example, the user may select 502whether the task is a new task or an existing task, such as via a dropdown menu or another graphical user interface element. In some aspects,a unique task identifier 504 may be generated and/or displayed to theuser. The user may provide a task description 508 for the task, such as“This task is used to execute action 1.” The task description maycomprise, for example, a sentence or phrase that a user, such as a userof the user device 151, can use to recognize the task. In some aspects,the user might not be provided with the option to update or create thetask description 508. The user may provide a task event trigger 510,which may identify a task (e.g., TASK1357) to be executed (e.g.,initiated or completed) prior to execution of the current task (e.g.,TASK123456). The user may select one or more dependent tasks via a dropdown menu or another graphical user interface. The drop down menu maylist, for example, existing tasks. In some aspects, the user may selectan option to add more dependencies, such as additional tasks to beexecuted prior to execution of the current task. Accordingly, amany-to-one task dependency may be implemented by the system describedherein. The user may provide a task time trigger 512, which may indicatethe time and/or date for the task to be executed, such as if the task isa time-based task. The user may select an option 514 to submit theupdated parameter values (or new parameter values) for the task. Inresponse, the computing device 101 may store the updated and/or newparameter values in a database, such as in the task registry 161 and/ordependent task registry 163.

FIG. 4 illustrates another example of at least a portion of a flowdiagram for triggering, managing, and/or controlling computing tasksbased on events and/or time factors in which various aspects of thedisclosure may be implemented. Execution of a task may be triggered byone or more events. In some aspects, a task may be triggered by anothertask. As previously described, a task may comprise a task that istriggered by the execution (e.g., initiation or completion) of one ormore other tasks. A task may be triggered based on a schedule, such asif a scheduled task time trigger elapses. In some aspects, a task may betriggered manually, such as from a user device and/or user interface(UI).

In step 402, the task management computing device 101 may determinewhether execution of a task is triggered by another task (e.g., theexecution, such as completion or initiation, of the other task). Thetrigger or dependent task(s) may comprise task(s) that are to beexecuted prior to execution of the current task. If the current task hasbeen triggered by the execution of another task, the computing device101 may proceed to step 408. Otherwise, the computing device 101 maywait for one or more trigger task to execute.

In step 404, the task management computing device 101 may determinewhether execution of a task is triggered based on a schedule, such as ascheduled time of execution. The scheduled time of execution maycomprise a time, that if exceeded, causes the computing device 101 toexecute the task. The scheduled time, which may be a predetermined time,may be modified by a user of the user device 151. In some aspects, thescheduled time of execution may comprise a time of day or a time period(e.g., every 15 minutes or every Thursday). Some tasks may include ascheduled execution time, and other tasks might not include a scheduledoverride time. In some aspects, the task management computing device 101may determine whether the current time exceeds the scheduled time forexecuting the task. If the task has been triggered by the scheduled timeof execution, the computing device 101 may proceed to step 408. If thecurrent time does not exceed the scheduled time for executing the taskor the task does not have a scheduled time for execution, the computingdevice may wait to receive a trigger for executing the task.

In some aspects, the task management computing device 101 may determineavailable processing resources, such as one or more server nodes 141 ornode clusters in the network 151, for executing the task. For example,the computing device 101 may determine the load of the availableprocessing resources for executing the task in the queue 171. The taskmanagement computing device 101 may determine, based on the availableprocessing resources, the amount of time to complete the task. Forexample, if the nodes 141 identified for executing the task areoverloaded (e.g., have loads that exceed threshold loads), the amount oftime to complete execution of the task may be higher. On the other hand,if the nodes 141 identified for executing the task are lightly loaded(e.g., have loads that are below threshold loads), the amount of time tocomplete execution of the task may be lower. The computing device 101may estimate the amount of time to complete the task. The taskmanagement computing device 101 may determine, based on the amount oftime to complete the task and based on an end time for completing thetask, a latest time to execute the task. For example, if the end timefor completing the task is 3 PM EST, and the amount of time to completethe task is 25 minutes, the computing device 101 may determine thelatest time to execute the task (e.g., the latest time to execute thetask) as 2:35 PM.

In some aspects, the latest time to execute the task may comprise thescheduled time to execute the task. In these examples, the taskmanagement computing device 101 may determine whether the current timeexceeds the latest time to execute the task. If the current time exceedsthe latest time to execute the task, the computing device 101 mayproceed to step 408 to attempt to execute the task. If the current timedoes not exceed the latest time to execute the task, the computingdevice 101 may wait for a trigger.

In step 406, the task management computing device 101 may determinewhether it received a manual task trigger from a user device and/or userinterface. In some aspects, a user of the user device 151 may provide amanual or override instruction to execute a task. The user device 151may transmit the override instruction to the computing device 101. Ifthe task has been triggered by a manual task trigger (e.g., thecomputing device 101 received the trigger from the user device 151and/or user interface), the computing device 101 may proceed to step 408to attempt to execute the current task. If a manual override has notbeen received, the computing device may wait for a trigger for thecurrent task. In some aspects, the computing device 101 may performsteps 402, 404, and/or 406 in parallel. For example, some tasks mayinclude one or more task trigger, one or more time trigger, and/or oneor more manual override trigger, and the computing device 101 maymonitor for each of the triggers.

In step 408, the task management computing device 101 may move (e.g.,load) the task into a task queue 171. For example, the task managementcomputing device 101 may move information for the task (e.g., taskidentifier, task dependencies, and the like) from the task registry 161to the task queue 171. The task management computing device 101 may alsodetermine (e.g., generate) a task sequence identifier (e.g., a number,such as a binary number) for the task. The generated task sequenceidentifier may comprise a unique task sequence identifier and may bestored into the associated task queue 171. The task sequence identifiermay be used to later identify, for example, the correct table entriesfor subsequent updates. The sequence identifier may be used to group aplurality of tasks, with each task in the group having the same sequenceidentifier. In some aspects, the task sequence identifier might beun-modifiable.

As previously described, one or more tasks may be moved to the taskqueue 171 based on one or more triggers, such as at certain times of theday (e.g., at predetermined times). In some aspects, the task may bemoved in response to a determination that the task will be executed inthe future, such as near future. The determination that the task will beexecuted in the near future may comprise a determination that thecurrent time is within a threshold time that the task is expected to beexecuted. The determination that the task will be executed in the nearfuture may additionally or alternatively comprise a determination thatone or more dependent tasks (e.g., tasks having an earlier sequencenumber than the task in question) has been initiated and/or will becompleted within a threshold amount of time. For example, if the task inquestion is to be executed fourth in a series of tasks, the taskmanagement computing device 101 may determine that the dependent taskimmediately preceding the task in question (e.g., the task to beexecuted third) has been initiated, is 50% complete, or is expected tobe completed within a threshold amount of time.

In step 410, the task management computing device 101 may load one ormore dependent task(s) into the dependent task queue 173. That is, thetask management computing device 101 may move information for dependenttasks from the dependent task registry 163 to the dependent task queue173. For example, the dependencies for the task loaded into the taskqueue 171 (e.g., in step 408) may be loaded into the dependent taskqueue 173, and may be associated with the same task sequence identifierthat was generated (e.g., in step 408) for the task loaded into the taskqueue 171. In some aspects, a task might not have any dependent tasks.In these scenarios, the computing device 101 might not load dependenttasks into the dependent task queue.

In step 412, the task management computing device 101 may determinewhether the dependent task(s) for the sequence identifier have beenexecuted (e.g., completed). For example, the task in the task queue 171may be verified to determine whether the task's dependencies have beencompleted (e.g., from the associated dependent task queue). If thedependent task(s) for the sequence identifier have been executed (step412: Y), the computing device 101 may proceed to step 422 to execute thetask in the task queue 171, as will be described in further detailbelow. If the dependent task(s) for the sequence identifier have notbeen executed (step 412: N), the computing device 101 may proceed tostep 414.

In step 414, the task management computing device 101 may determinewhether a task due out time has been exceeded. For example, a task maycomprise an indicator for which the task may become stale (e.g., aftersitting in the queue 3 days). If the task is in the queue and has notbeen executed by the due out time, the computing device 101 maydetermine, in step 414, that the task due out time has been exceeded. Ifthe task due out time has not been exceeded (step 414: N), the computingdevice 101 may proceed to step 420, as will be described in furtherdetail below. If the task due out time has been exceeded (step 414: Y),the computing device 101 may proceed to step 416.

In step 416, the task management computing device 101 may determinewhether an alert has previously been sent to the user device 151 and/ora user interface. If the alert was previously sent to the user device151 and/or a user interface (step 416: Y), the computing device 101 mayproceed to step 420. If the alert has not been sent to the user device151 and/or a user interface (step 416: N), the computing device 101 mayproceed to step 418.

In step 418, the task management computing device 101 may transmit analert to the user device 151 and/or a user interface, and the alert mayindicate that a task is late. In some aspects, the alert may indicatethat the due out time has been exceeded for the task and that taskexecution is now late. In some aspects, the user may manually resolvethe unexecuted task, such as by marking the task as complete or manuallyinstructing, via the user device 151, the computing device 101 toexecute that task.

In step 420, the task management computing device 101 may wait an amountof time, which may be configurable. A user of the user device 151 mayconfigure the amount of time to wait in step 420.

In step 421, the task management computing device 101 may determinewhether a manual override for a dependent task has been received (e.g.,for a dependent task having the sequence ID of the task in the taskqueue 171). If a manual override for a dependent task has been received,the computing device 101 may update the dependency data (e.g., to markthe dependent task as completed). The computing device 101 may return tostep 412 to again check the status of the task and eligibility forexecution.

In step 422, the task management computing device 101 may execute (orcause execution of) the task in the task queue 171 if the task iseligible for execution. For example, the dependent task(s) for thesequence ID of the task in the task queue 171 may have been executed.The computing device 101 may assign the task to one or more processingresources (e.g., a server node 141 or cluster of server nodes) and mayinstruct the server node(s) 141 to execute the task.

In step 424, the task management computing device 101 may mark the taskas complete in the dependent task queue 173. For example, other tasks inthe queues containing this completing task as a dependency may have thedependency set to complete. Marking the task as complete may trigger theexecution of one or more other tasks. The task management computingdevice 101 may continue to step 428, as will be described in furtherdetail below.

In some aspects, in step 426, the task management computing device 101may determine whether it has received a manual task completion override,such as from the user device 151 and/or a UI. The manual completionoverride received from a UI may comprise an operator action. If a manualtask completion override has been received, the computing device 101 mayproceed to step 424, as previously described.

In step 428, the task management computing device 101 may remove theexecuted task from the task queue 171. In some aspects, the removal maycomprise a virtual removal of the task, such that the task remains inthe task queue 171, but the task is marked as complete. By maintainingthe task in the task queue 171, a record of task execution andassociated data (e.g., time of execution, duration of execution,bandwidth and/or resources used, and other data) may be created.

In step 430, the task management computing device 101 may determinewhether the executed task triggers one or more other tasks. That is, thecomputing device 101 may determine whether or not the completing task isto trigger one or more other tasks. If not (step 430: N), the computingdevice 101 may continue to step 434. Otherwise, the computing device mayproceed to step 432.

In step 432, the task management computing device 101 may trigger one ormore other tasks (e.g., a plurality of tasks), such that the one or moreother tasks are marked to be added to the task queue 171. For example(and as previously described with respect to step 402), the completingtask may trigger the tasks as configured within the task registry 161 tobe brought into the task queues. The task management computing device101 may continue to step 402 for these other triggered tasks.

Otherwise, in step 434, the task management computing device 101 may endthe process for the completed task. That is, the completing task maycome to the end of its processing, and no further activity is taken forthe task.

Various aspects described herein may be embodied as a method, anapparatus, or as computer-executable instructions stored on one or morenon-transitory and/or tangible computer-readable media. Any and/or allof the method steps described herein may be embodied incomputer-executable instructions stored on a computer-readable medium,such as a non-transitory and/or tangible computer readable medium and/ora computer readable storage medium. Additionally or alternatively, anyand/or all of the method steps described herein may be embodied incomputer-readable instructions stored in the memory and/or othernon-transitory and/or tangible storage medium of an apparatus thatincludes one or more processors, such that the apparatus is caused toperform such method steps when the one or more processors execute thecomputer-readable instructions. In addition, various signalsrepresenting data or events as described herein may be transferredbetween a source and a destination in the form of light and/orelectromagnetic waves traveling through signal-conducting media such asmetal wires, optical fibers, and/or wireless transmission media (e.g.,air and/or space).

Aspects of the disclosure have been described in terms of illustrativeembodiments thereof. Numerous other embodiments, modifications, andvariations within the scope and spirit of the appended claims will occurto persons of ordinary skill in the art from a review of thisdisclosure. For example, one of ordinary skill in the art willappreciate that the steps illustrated in the illustrative figures may beperformed in other than the recited order, and that one or more stepsillustrated may be optional in accordance with aspects of thedisclosure.

What is claimed is:
 1. A system comprising: a task registry; a taskqueue; a dependent task queue; a user device configured to: receive,from a user, task information, the task information including dependencyinformation about a plurality of dependent computing tasks for a firstcomputing task; and transmit, to a computing device, the taskinformation about the plurality of dependent computing tasks for thefirst computing task; the computing device comprising: a processor; andmemory storing computer-executable instructions that, when executed bythe processor, cause the computing device to: receive, from the userdevice, the task information, the task information including dependenttask information about the plurality of dependent computing tasks;store, at the task registry and in association with the first computingtask, the task information; cause a first transmission of the taskinformation about the first computing task from the task registry to thetask queue; cause a second transmission of the dependency informationabout the plurality of dependent computing tasks from the task registryto the dependent task queue, wherein the causing the first transmissionof the first computing task from the task registry to the task queue isperformed before the causing the second transmission of the plurality ofdependent computing tasks from the task queue to the dependent taskqueue; determine whether the plurality of dependent computing tasks hasbeen executed wherein the first computing task is executed after theplurality of dependent computing tasks is executed; and when theplurality of dependent computing tasks has been executed, determine oneor more nodes for executing the first computing task and causetransmission of an execution request of the first computing task fromthe task queue to the one or more nodes for executing the firstcomputing task; and the one or more nodes configured to: execute thefirst computing task in response to receiving the first computing taskfrom the task queue.
 2. The system of claim 1, wherein the determiningwhether the plurality of dependent computing tasks has been executedcomprises determining whether execution of the plurality of dependentcomputing tasks has been completed by one or more nodes.
 3. The systemof claim 1, wherein the determining whether the plurality of dependentcomputing tasks has been executed comprises determining whetherexecution of the plurality of dependent computing tasks has beeninitiated by one or more nodes.
 4. The system of claim 1, wherein thememory of the computing device stores computer-executable instructionsthat, when executed by the processor, cause the computing device to:determine whether the computing device has received a manual overridefrom the user device; and if the computing device has received themanual override from the user device, determine one or more nodes forexecuting the first computing task and cause transmission of the firstcomputing task from the task queue to the one or more nodes forexecuting the first computing task.
 5. The system of claim 1, whereinthe memory of the computing device stores computer-executableinstructions that, when executed by the processor, cause the computingdevice to: determine whether a current time exceeds a scheduled time toexecute the first computing task; and if the current time exceeds thescheduled time to execute the first computing task, determine one ormore nodes for executing the first computing task and cause transmissionof the first computing task from the task queue to the one or more nodesfor executing the first computing task.
 6. The system of claim 1,wherein the memory of the computing device stores computer-executableinstructions that, when executed by the processor, cause the computingdevice to: determine one or more nodes for executing the first computingtask; determine, based on the one or more nodes for executing the firstcomputing task, an amount of time to complete execution of the firstcomputing task; and determine, based on the amount of time to completeexecution of the first computing task, a latest time to execute thefirst computing task.
 7. A method comprising: receiving, by a computingdevice and from a user device, task information, the task informationincluding dependency information about a plurality of dependentcomputing tasks for a first computing task; storing, by the computingdevice, at a task registry, and in association with the first computingtask, the task information; causing, by the computing device, a firsttransmission of the task information about the first computing task fromthe task registry to a task queue; causing a second transmission of thedependency information about the plurality of dependent computing tasksfrom the task registry to a dependent task queue, wherein the causingthe first transmission of the first computing task from the taskregistry to the task queue is performed before the causing the secondtransmission of the plurality of dependent computing tasks from the taskqueue to the dependent task queue; determining, by the computing device,whether the plurality of dependent computing tasks has been executed,wherein the first computing task is executed after the plurality ofdependent computing tasks is executed; when the plurality of dependentcomputing tasks has been executed, determining, by the computing device,one or more nodes for executing the first computing task and causing, bythe computing device, transmission of an execution request of the firstcomputing task from the task queue to the one or more nodes forexecuting the first computing task; and executing, by the one or morenodes, the first computing task in response to receiving the firstcomputing task from the task queue.
 8. The method of claim 7, whereinthe determining whether the plurality of dependent computing tasks hasbeen executed comprises determining whether execution of the pluralityof dependent computing tasks has been completed by one or more nodes. 9.The method of claim 7, wherein the determining whether the plurality ofdependent computing tasks has been executed comprises determiningwhether execution of the plurality of dependent computing tasks has beeninitiated by one or more nodes.
 10. The method of claim 7, furthercomprising: determining, by the computing device, whether the computingdevice has received a manual override from the user device; and if thecomputing device has received the manual override from the user device,determining, by the computing device, one or more nodes for executingthe first computing task and causing, by the computing device,transmission of the first computing task from the task queue to the oneor more nodes for executing the first computing task.
 11. The method ofclaim 7, further comprising: determining, by the computing device,whether a current time exceeds a scheduled time to execute the firstcomputing task; and if the current time exceeds the scheduled time toexecute the first computing task, determining, by the computing device,one or more nodes for executing the first computing task and causing, bythe computing device, transmission of the first computing task from thetask queue to the one or more nodes for executing the first computingtask.
 12. The method of claim 7, further comprising: determining, by thecomputing device, one or more nodes for executing the first computingtask; determining, by the computing device and based on the one or morenodes for executing the first computing task, an amount of time tocomplete execution of the first computing task; and determining, by thecomputing device and based on the amount of time to complete executionof the first computing task, a latest time to execute the firstcomputing task.
 13. The method of claim 7, wherein a second computingtask has a dependency on the first computing task and the secondcomputing task is in the task queue, the method further comprising: whenthe first computing task completes execution, marking the firstcomputing task as complete in the dependent task queue.
 14. The methodof claim 7, the method further comprising: when the first computing taskcompletes execution, triggering a third computing task; and in responseto the triggering, repeating the receiving, the storing, the causing thefirst transmission, the causing the second transmission, the determiningwhether the plurality of dependent computing tasks has been executed,and the determining one or more modes for executing for the thirdcomputing task.
 15. The method of claim 7, the method furthercomprising: when the first computing task completes execution, virtuallyremoving the first computing task from the task queue, wherein the firstcomputing task remains in the task queue and is marked as complete. 16.A non-transitory computer readable medium storing instructions thereonthat, when read by a computing device, causes the computing device to:receive, from a user device, task information, wherein the taskinformation includes dependency information about a plurality ofdependent computing tasks for a first computing task; store, at a taskregistry and in association with the first computing task, the taskinformation; cause a first transmission of the task information aboutthe first computing task from the task registry to a task queue; cause asecond transmission of the dependency information about the plurality ofdependent computing tasks from the task registry to a dependent taskqueue, wherein the causing the first transmission of the first computingtask from the task registry to the task queue is performed before thecausing the second transmission of the plurality of dependent computingtasks from the task queue to the dependent task queue; determine whetherthe plurality of dependent computing tasks has been executed, whereinthe first computing task is executed after the plurality of dependentcomputing tasks is executed; when the plurality of dependent computingtasks has been executed, determine one or more nodes for executing thefirst computing task and cause transmission of an execution request ofthe first computing task from the task queue to the one or more nodesfor executing the first computing task; and execute, by the one or morenodes, the first computing task in response to receiving the firstcomputing task from the task queue.
 17. The non-transitory computerreadable medium of claim 16, wherein the determining whether theplurality of dependent computing tasks has been executed comprisesdetermining whether execution of the plurality of dependent computingtasks has been completed by one or more nodes.
 18. The non-transitorycomputer readable medium of claim 16, wherein the determining whetherthe plurality of dependent computing tasks has been executed comprisesdetermining whether execution of the plurality of dependent computingtasks has been initiated by one or more nodes.
 19. The non-transitorycomputer readable medium of claim 16, storing instructions thereon that,when read by the computing device, causes the computing device to:determine whether the computing device has received a manual overridefrom the user device; and if the computing device has received themanual override from the user device, determine one or more nodes forexecuting the first computing task and cause transmission of the firstcomputing task from the task queue to the one or more nodes forexecuting the first computing task.
 20. The non-transitory computerreadable medium of claim 16, storing instructions thereon that, whenread by the computing device, causes the computing device to: determinewhether a current time exceeds a scheduled time to execute the firstcomputing task; and if the current time exceeds the scheduled time toexecute the first computing task, determine one or more nodes forexecuting the first computing task and cause transmission of the firstcomputing task from the task queue to the one or more nodes forexecuting the first computing task